Task: Sprint review
Show what has been done and works. Draw consequences.
Disciplines: Scrum Activities
Purpose
The goal is to show the done requirements during the sprint with a demo of the partial product
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory: Optional:
  • None
Outputs
Steps
Prepare the demo
The meeting preparation must not exceed one hour.
Perform the demo
The team presents the partial product, result of its development tasks, through a demo of the implemented requirements (user stories). Only fully completed (and tested) requirement implementations (et testées) are presented. This allows to get an objective measurement of the work progress.
Evaluate Sprint results

The Product Owner and attending stakeholders (customers, users) ask questions to the team, give impressions, make proposals and change requests. The Product Backlog is enhanced with found bugs and enhancement requests.

Calculate actual velocity

The Sprint Velocity is the sum of all associated points to requirements checked as fully implemented. It is then compared to the one from previous sprints, usually through a Release Burndown Chart.

Adjust the Release planning

Conditions may have changed since the last release planning:

  • items may have been added, or deleted, estimations updated, 
  • item prioritization has been changed,

in addition, average velocity may have evolved. 

The Release planning is adjusted, taking into account these new parameters.

Key Considerations

Team work (during the Sprint review meeting)

For the meeting:

  • max length:  2 hours
  • average length: 1 hour
This program and its materials are provided under the terms of the "Eclipse Public License v1.0" license.